Alena Ventrallis
Ahrendee Inc.
Negative-Feedback
2971
   |
Posted - 2015.04.08 00:26:00 -
[1] - Quote
So something I notice when we talk about framerate lag. I believe we are looking into the wrong area when we try to fix the lag. Now so far we have been looking at various areas, like comm channels and such, as possible fixes for the lag. However, I think the problem is down further in the code: a memory leak.
Here's my line of thought: if it was comms that was causing the problems, or number of suit fittings, we would see framerate lag spread out evenly over the entire match from start to finish. But instead, we have the match start out fine and get steadily worse as it progresses. This is most noticeable on Gallente Research Facility. Next time you deploy, notice how you deploy just like normal, but as you fight, the lag gets worse and worse and worse. This is symptomatic of a memory leak, although there are other possible reasons for this behavior.
Wikipedia decribes a memory leak as "a type of resource leak that occurs when a computer program incorrectly manages memory allocations[1] in such a way that memory which is no longer needed is not released." Imagine your PS3's memory (RAM) as table-space. The more RAM you have, the bigger your table. Now, when you use your table (say, to paint), after you finish whatever you are doing, you then put the stuff back in its place to keep the table clear for the next task (you put your paint and paper back in the closet). This is what your computer does with RAM; once it's done using RAM for one part of a program, it releases it so it can be used for another part of the program. Now a memory leak happens when your computer doesn't release the RAM like it should. Going back to the table analogy, it would be like leaving all the stuff you last used sitting on the table. So when you want to do something else with the table (like eating) all the paint and paper and brushes and stuff are still on the table in your way. This means your computer has less table-space to work with, which then causes the program to start run slower and slower as it has less and less RAM to work with..
Now, there are other possible causes for this behavior, and it would take a n actual programmer to disgnose and fix a memory leak if indeed it is one. It could also be that the game needs to clear its cahce more often. But I don't believe the framerate problems we are experiencing are because of comms or number of fittings. IF so, wouldn't we see lag happen as soon as the match begins instead of partially into it? So this is something Rattati can look into as a possible cause for the horrid framerate lag we are experiencing.
Whirly gun make much thunder! - Victor
|